home
***
CD-ROM
|
disk
|
FTP
|
other
***
search
/
Grand Slam 3
/
Grand Slam 3.iso
/
002
/
fe145.arj
/
UPGRADE.DOC
< prev
next >
Wrap
Text File
|
1995-06-30
|
6KB
|
125 lines
FastEcho 1.45 UPGRADE notice
============================
* make a backup of your current configuration and the executables
* extract ALL files from the FastEcho 1.45 archive(s)
* run FESetup and go through all menues to see what's new and what has
to be changed manually, there are some new options which may interfere
with your old configuration (check the ARCmail sizing info below) !
* save the new configuration (done automatically by FESetup) ! MANDATORY !
Information on the new ARCmail sizing:
You can define the values in two places: the default under FESetup/Setup/
Parameters, which will be taken for all the systems which have a '0' in the
Max. ARCmail size field of the node manager. If you specify -1 as Max. size
in the node manager, only one (unlimited) archive will be created for that
system just the way it used to be in previous versions. Same happens if you
set both values to '0'.
The way it works, while still being able to use the 'List' prefix:
You can (have to) specify the average compression ratio for each archiver
in tenths (an average of 1:3.5 means 10:35 so you have to enter a 35 in
that field in Compression programs, it's calculated by 'size of .PKTs'
divided by 'size of archive'). In the main compression loop FE will try to
pack as many .PKTs in one archive by calculating the expected compressed
size according to the ratio level specified. If the calculated value exceeds
the selected maximum, it will call the archiver. If afterwards (due to a too
low ratio specified for example) the archive is still smaller than the
maximum, FE will try to add more .PKTs to it as well, but only if the
difference of (calcsize minus currentsize) is smaller than (maxsize minus
currentsize), so that it will create sligthly bigger archives rather than
significant smaller ones. In any other case it will create a new archive.
So to make this way as efficient as possible, correct values have to be set
up for each archiver. If the ratio field is set to 0, FE will work with a
default value of 32 (which is 1:3.2) ...
Suggested values for the usual archivers (standard compression used):
UC2: 40, RAR: 35, ZIP/ARJ/SQZ: 34, LHA: 32, PAK: 30,
LZH: 29, ZOO: 20, ARC: 18
These values may vary depending on what kind of mail you process (FidoNet,
Internet newsgroups etc.). If you see that FastEcho frequently adds 1 more
.PKT to an archive after adding a couple others and before starting a new
archive, set the value higher. The next version probably will include an
algorithm adjusting the values on the fly without manual intervention.
Together with a well selected 'Maximum .PKT size' this algorithm will create
pretty constant archive sizes with a variation of only some percent.
BTW, for some functions (ie. the selection of the new archive extension)
it is more or less vital that the archiver is NOT told to set the archive
timestamp to the time/date of the 'youngest' file included, in most cases
(99.9%) it doesn't make any difference in FE's operation, but in some rare
cases it CAN make one and IMHO this function doesn't make much sense anyway.
Information on the new DPMI version:
DPMI 16 bit versions (compiled for a i386 CPU or higher) are now available,
you will need to have RTM.EXE and DPMI16BI.OVL either in your current
directory or in your PATH. There are following compatibility problems
you can run into unless you use another DPMI server (OS/2 or QDPMI
for example) rather than the included one:
- PKZip 2.04 needs the -3 switch or it will hang occasionally,
in certain environments it might be a good idea to disable
PKZip's DPMI support with the -) switch
- .EXEs hang when running under DESQview (QDPMI works fine)
Other considerations when running the 16 bit DPMI version:
- you can't call external programs (like packet sorters) which
use their own DOS extender (like DOS4GW), run them before or
after you run FASTEC16.EXE rather than as 'After Unpack' or
'Before Pack' ...
- you need a certain amount of free memory (conventional and
extended). Otherwise - even though it doesn't exit with 'out
of memory' - the program will be very slow (because it
continuosly has to swap the overlays) or even occasionally hang.
This amount depends on your setup, of course. If you notice that
it takes for example 10-20 seconds for the program logo to appear
when you call it manually, you can be almost sure that there isn't
enough memory. ;-) Furthermore, if you are low on memory,
FastEcho/16 will probably not be able to call the compression
programs and return an error code (or even hang).
Differences between the real mode and the 16 bit DPMI version:
- plenty of free memory ;-)
- a bit slower in several places (because it has to switch from
protected to real mode every time it calls DOS interrupts)
- allows up to 262000 dupe records but needs more memory than
the real mode version for the same number of records - but it
is a lot faster than the EMS and XMS support
DPMI Runtime Module options
SET RTM=[OPTION nnnn [OPTION nnnn [...]]]
Where OPTION might be:
EXTLEAVE nnnn leave at least nnnn kB of free Extended memory
EXTMAX nnnn don't use more than nnnn kB of Extended memory
EXTMIN nnnn exit if less than nnnn kB of Extended memory are avail
REALLEAVE nnnn leave at least nnnn _segments_ of free normal memory
REALMAX nnnn (same as EXTMAX/EXTMIN, but with real mode memory
REALMIN nnnn _segments_, 1 segment = 16 byte)
Example:
SET RTM=EXTMAX 2048 REALLEAVE 8192
= don't use more than 2MB extended memory and leave at least 128kB of
conventional memory free (for executing archivers for example)
[EOF]